|
|
|
|
|
|
|
In the Account class, this method call would then have the following uses relationship: |
|
|
|
|
|
|
|
|
Public Sub verifyCheckAccountHistory(SomeCustomerSSN)
theCheckingAccountHistoryInfo.verify(SomeCustomerSSN)
End Sub |
|
|
|
|
|
|
|
|
In most cases, the uses relationship resembles delegation, in which an object delegates one or all of its responsibilities to another object. |
|
|
|
|
|
|
|
|
The Booch method is primarily concerned with discovering the chief abstractions (or areas of specialized focus) of classes and objects as parts of the overall system in your problem domain. The identification process examines the vocabulary of the business domain, much the way OOSE does. Booch also looks at the contextual meaning of these classes and objects and how they are used by others. Grasping the meaning of classes and objects is by no means an easy process and requires many iterations through design and analysis. Thus, domain experts become critical stakeholders in the production of analysis and design models and other artifacts. |
|
|
|
|
|
|
|
|
Finally, Booch divides the system into several views and models. Among the views are the Logical View and the Physical View (which are the basis of Microsoft's Visual Modeler). The Logical View encompasses the structure of and relationships between classes and objects. The Physical View encompasses the actual file location of the classes in the Logical View. |
|
|
|
| | UML stands for Unified Modeling Language. Its notation represents the combination of the most important object-oriented methodologies in the software development community today. The three top methodologistsIvar Jacobson, Jim Rumbaugh, and Grady Boochare the chief architects of UML. The UML creation process began in late 1994 when Booch and Rumbaugh collaborated to unify their respective methodologies. Jacobson joined them shortly thereafter. | | The UML doesn't represent an elimination of OOSE, OMT, or the Booch method, as some have suggested. Instead, it represents a unified way of modeling elements in each. Of course, the UML creation process has led to some version upgrades in the top three methodologies, but the UML only represents a standard way to express each one. | | The UML is wholly encapsulated within the Rational Rose automation tool. This should not be surprising because Jacobson, Booch, and Rumbaugh are the joint chiefs of Rational Corporation. Because UML and Rational Rose 4.0 are so tightly intertwined, I'll discuss more details of the UML in the section on Rational Rose later. For now, suffice it to say that the UML incorporates four views of the system: | | Use Case View | | Logical View |
|
|
|
|
|
(text box continued on next page) |
|
|
|
|
|